Rejection notification to the uicc

ABSTRACT

Registration rejections are reported to a universal integrated circuit card (UICC). Remote access can be provide to registration rejection data stored in the UICC, the registration rejection data can be transmitted to a service provider, one or more UICC applications can be executed based on the registration rejection data, and/or the registration rejection data can be logged or tracked. In addition, action taken by the UICC can be automated based on the registration rejection using artificial intelligence.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of, and claims priority toeach of, U.S. patent application Ser. No. 14/603,116, filed on Jan. 22,2015, and entitled “REJECTION NOTIFICATION TO THE UICC”, which is acontinuation of U.S. patent application Ser. No. 12/242,019, filed onSep. 30, 2008, now issued as U.S. Pat. No. 8,971,884, and entitled“REJECTION NOTIFICATION TO THE UICC”. The entireties of the foregoingapplications are hereby incorporated by reference herein.

TECHNICAL FIELD

The subject application relates generally to the telecommunicationsindustry, and more particularly to apparatus and methodologies forsending rejection notifications to the UICC.

BACKGROUND

Optimization of network coverage and service quality are constant goalsfor wireless network operators. Superior coverage and service qualityresults in enhanced user experiences, greater throughput, and ultimatelyincreased revenue. One way to achieve superior coverage and servicequality is through increased access management and reporting capability.

The ability to quickly and consistently diagnosis access andconnectivity issues is of high monetary significance for serviceproviders, and is generally desirable for efficient and effectivehandling of technical issues. This is largely dependent on the abilityto accurately retrieve desired information or data regarding networkconnectivity. Currently, when a mobile device's attempted registrationis rejected from a network it can be difficult for the service providerto ascertain why the rejection occurred. Sometimes the rejections arevalid, and other times the rejections can be accidental.

Often times when a registration attempt is rejected, the mobile devicewill display a message to the user. However, the inability of serviceproviders to consistently and quickly determine why a rejection hasoccurred can cause unnecessary subscriber downtime, as well as consumerfrustration. Unfortunately, conventional techniques do not provide forconsistent and convenient determination of the causes of a registrationrejection.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary multiple access wireless communicationsystem in accordance with an aspect of the subject specification.

FIG. 2 illustrates a general block diagram of a communication system inaccordance with an aspect of the subject specification.

FIG. 3 illustrates an exemplary wireless communication system inaccordance with an aspect of the subject specification.

FIG. 4 is a general component block diagram illustrating a wirelessnetwork in accordance with an aspect of the present application.

FIG. 5 illustrates an example general component block diagram of amobile device in accordance with the subject application

FIG. 6 illustrates an example general component block diagram of UICCcomponent in accordance with an aspect of the subject application.

FIG. 7 illustrates an example envelope facilitating for rejectionnotification to the UICC in accordance with an aspect of the subjectapplication.

FIG. 8 illustrates an example methodology in accordance with an aspectof the subject application.

FIG. 9 illustrates an approach that employs an artificial intelligencecomponent which facilitates automating one or more features inaccordance with an alternative embodiment.

FIG. 10 illustrates an exemplary device operative to execute the one ormore embodiments disclosed herein.

DETAILED DESCRIPTION

The claimed subject matter is now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the claimed subject matter. It may beevident; however, that such matter can be practiced without thesespecific details. In other instances, well-known structures and devicesare shown in block diagram form in order to facilitate describing theclaimed subject matter.

As used in this application, the terms “component” and “system” areintended to refer to a computer-related entity, either hardware, acombination of hardware and software, software, or software inexecution. For example, a component can be, but is not limited to being,a process running on a processor, a processor, a hard disk drive,multiple storage drives (of optical and/or magnetic storage medium), anobject, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components canreside within a process and/or thread of execution, and a component canbe localized on one computer and/or distributed between two or morecomputers.

In one embodiment, a mobile device is disclosed including a registrationcomponent that obtains a registration rejection notification, and auniversal integrated circuit card (UICC) component that at least one ofstores data associated with the registration rejection notification,instructs the mobile device based at least in part on the registrationrejection notification, or transmits data associated with theregistration rejection notification.

In yet another embodiment, a method is disclosed including the steps ofobtaining a registration rejection message, analyzing the registrationrejection message; and determining at least one action based at least inpart on a set of data related to the registration rejection message(registration rejection data) using a universal integrated circuit card(UICC).

In an alternative embodiment, a system is disclosed including means forobtaining a registration rejection message, means for analyzing theregistration rejection message, and means for determining a course ofaction based at least in part on the registration rejection messageusing a universal integrated circuit card (UICC).

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative, however, of but a few of the various ways in which theprinciples disclosed herein can be employed and is intended to includeall such aspects and their equivalents. Other advantages and novelfeatures will become apparent from when considered in conjunction withthe drawings.

Referring initially to the drawings, FIG. 1 Referring now to FIG. 1, awireless communication system 100 is illustrated in accordance withvarious embodiments presented herein. System 100 comprises a basestation 102 that can include multiple antenna groups. For example, oneantenna group can include antennas 104 and 106, another group cancomprise antennas 108 and 110, and an additional group can includeantennas 112 and 114. Two antennas are illustrated for each antennagroup; however, more or fewer antennas can be utilized for each group.Base station 102 can additionally include a transmitter chain and areceiver chain, each of which can in turn comprise a plurality ofcomponents associated with signal transmission and reception (e.g.,processors, modulators, multiplexers, demodulators, demultiplexers,antennas, etc.), as will be appreciated by one skilled in the art.

Base station 102 can communicate with one or more mobile devices such asmobile device 116 and mobile device 122; however, it is to beappreciated that base station 102 can communicate with substantially anynumber of mobile devices similar to mobile devices 116 and 122. Mobiledevices 116 and 122 can be, for example, cellular phones, smart phones,laptops, handheld communication devices, handheld computing devices,satellite radios, global positioning systems, PDAs, and/or any othersuitable device for communicating over wireless communication system100. As depicted, mobile device 116 is in communication with antennas112 and 114, where antennas 112 and 114 transmit information to mobiledevice 116 over a forward link 118 and receive information from mobiledevice 116 over a reverse link 120. Moreover, mobile device 122 is incommunication with antennas 104 and 106, where antennas 104 and 106transmit information to mobile device 122 over a forward link 124 andreceive information from mobile device 122 over a reverse link 126. In afrequency division duplex (FDD) system, forward link 118 can utilize adifferent frequency band than that used by reverse link 120, and forwardlink 124 can employ a different frequency band than that employed byreverse link 126, for example. Further, in a time division duplex (TDD)system, forward link 118 and reverse link 120 can utilize a commonfrequency band and forward link 124 and reverse link 126 can utilize acommon frequency band.

Each group of antennas and/or the area in which they are designated tocommunicate can be referred to as a sector of base station 102. Forexample, antenna groups can be designed to communicate to mobile devicesin a sector of the areas covered by base station 102. In communicationover forward links 118 and 124, the transmitting antennas of basestation 102 can utilize beamforming to improve signal-to-noise ratio offorward links 118 and 124 for mobile devices 116 and 122. This can beprovided by using a precoder to steer signals in desired directions, forexample. Also, while base station 102 utilizes beamforming to transmitto mobile devices 116 and 122 scattered randomly through an associatedcoverage, mobile devices in neighboring cells can be subject to lessinterference as compared to a base station transmitting through a singleantenna to all its mobile devices. Moreover, mobile devices 116 and 122can communicate directly with one another using a peer-to-peer or ad hoctechnology in one example.

According to an example, system 100 can be a multiple-inputmultiple-output (MIMO) communication system. Further, system 100 canutilize substantially any type of duplexing technique to dividecommunication channels (e.g., forward link, reverse link, . . . ) suchas FDD, TDD, and the like. Moreover, the system 100 can be amultiple-bearer system. A bearer can be an information path of definedcapacity, delay, bit error rate, etc. Mobile devices 116 and 122 caneach serve one or more radio bearers. The mobile devices 116 and 122 canemploy uplink rate control mechanisms to manage and/or share uplinkresources across the one or more radio bearers. In one example, themobile devices 116 and 122 can utilize token bucket mechanisms to servethe radio bearers and to enforce uplink rate limitations.

Pursuant to an illustration, each bearer can have an associatedprioritized bit rate (PBR), maximum bit rate (MBR) and guaranteed bitrate (GBR). The mobile devices 116 and 122 can serve the radio bearersbased, at least in part, on the associated bit rate values. The bit ratevalues can also be employed to calculate queue sizes that account forPBR and MBR for each bearer. The queue sizes can be included in uplinkresource requests transmitted by the mobile devices 116 and 122 to thebase station 102. The base station 102 can schedule uplink resources formobile device 116 and 122 based upon respective uplink requests andincluded queue sizes.

FIG. 2 is a block diagram of an embodiment of a transmitter system 210(also known as the access point) and a receiver system 250 (also knownas access terminal) in a MIMO system 200. At the transmitter system 210,traffic data for a number of data streams is provided from a data source212 to a transmitter (TX) data processor 214.

In an embodiment, each data stream is transmitted over a respectivetransmit antenna. TX data processor 214 formats, codes, and interleavesthe traffic data for each data stream based on a particular codingscheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot datausing OFDM techniques. The pilot data is typically a known data patternthat is processed in a known manner and may be used at the receiversystem to estimate the channel response. The multiplexed pilot and codeddata for each data stream is then modulated (i.e., symbol mapped) basedon a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or M-QAM)selected for that data stream to provide modulation symbols. The datarate, coding, and modulation for each data stream may be determined byinstructions performed by processor 230.

The modulation symbols for all data streams are then provided to a TXMIMO processor 220, which may further process the modulation symbols(e.g., for OFDM). TX MIMO processor 220 then provides N_(T) modulationsymbol streams to N_(T) transmitters (TMTR) 222 a through 222 t. Incertain embodiments, TX MIMO processor 220 applies beamforming weightsto the symbols of the data streams and to the antenna from which thesymbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel. N_(T)modulated signals from transmitters 222 a through 222 t are thentransmitted from N_(T) antennas 224 a through 224 t, respectively.

At receiver system 250, the transmitted modulated signals are receivedby N_(R) antennas 252 a through 252 r and the received signal from eachantenna 252 is provided to a respective receiver (RCVR) 254 a through254 r. Each receiver 254 conditions (e.g., filters, amplifies, anddownconverts) a respective received signal, digitizes the conditionedsignal to provide samples, and further processes the samples to providea corresponding “received” symbol stream.

An RX data processor 260 then receives and processes the N_(R) receivedsymbol streams from N_(R) receivers 254 based on a particular receiverprocessing technique to provide N_(T) “detected” symbol streams. The RXdata processor 260 then demodulates, deinterleaves, and decodes eachdetected symbol stream to recover the traffic data for the data stream.The processing by RX data processor 260 is complementary to thatperformed by TX MIMO processor 220 and TX data processor 214 attransmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use(discussed below). Processor 270 formulates a reverse link messagecomprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message is then processed by a TX data processor 238, whichalso receives traffic data for a number of data streams from a datasource 236, modulated by a modulator 280, conditioned by transmitters254 a through 254 r, and transmitted back to transmitter system 210.

At transmitter system 210, the modulated signals from receiver system250 are received by antennas 224, conditioned by receivers 222,demodulated by a demodulator 240, and processed by a RX data processor242 to extract the reserve link message transmitted by the receiversystem 250. Processor 230 then determines which pre-coding matrix to usefor determining the beamforming weights then processes the extractedmessage.

FIG. 3 illustrates an exemplary wireless communication system 300configured to support a number of users, in which various disclosedembodiments and aspects may be implemented. As shown in FIG. 3, by wayof example, system 300 provides communication for multiple cells 302,such as, for example, macro cells 302 a-302 g, with each cell beingserviced by a corresponding access point (AP) 304 (such as APs 304 a-304g). Each cell may be further divided into one or more sectors (e.g. toserve one or more frequencies). Various access terminals (ATs) 306,including ATs 306 a-306 k, also known interchangeably as user equipment(UE) or mobile stations, are dispersed throughout the system. Each AT306 may communicate with one or more APs 304 on a forward link (FL)and/or a reverse link (RL) at a given moment, depending upon whether theAT is active and whether it is in soft handoff, for example. Thewireless communication system 300 may provide service over a largegeographic region, for example, macro cells 302 a-302 g may cover a fewblocks in a neighborhood.

The cells 302 can provide coverage via a plurality of networks, such asGSM/GPRS/Edge network (hereinafter referred to as “2G network”), and/orUMTS network (hereinafter referred to as “WCDMA coverage,” “3G network,”or simply as “3G”). The system 300 can have a first network in thecells, wherein the first network is the most readily available network,or can be considered the “fall back” technology having the greatestcoverage area. In addition, the system 300 may have a second networkthat is available in a subset of the cells 302, and is not as readilyavailable as the first network. For example, the second network may notbe available in each cell 302, and/or may not cover the entire area ofthe cells 302 in which it is available. Users leaving the second networkare provided coverage by the first network. For instance, the system 300can include 2G and 3G networks, wherein the 2G network covers the entiresystem 300, and the 3G network is available in some locations throughoutthe system 300.

FIG. 4 illustrates an example wireless communication system 400 inaccordance with an aspect of the subject application. The wirelesscommunication system 400 includes a mobile device 402, a serving network404, and a home network 406. The mobile device 402 can be a UE (aspreviously discussed), a wireless phone, a smart phone, a PDA, a laptop,and so forth. In operation, the mobile device 402 sends, transmits, orotherwise communicates one or more registration messages (not shown) tothe serving network 404 via a communication link 408. The registrationmessage can include most any of a plurality of registration data, suchas mobile device identifier, a subscriber identifier, subscription data,and so forth. In addition, the registration message can include a typeof registration requested, such as a circuit switched registration (e.g.voice communication) or a packet switched registration (e.g. datacommunication).

The serving network 404 can provide wireless service to one or moremobile devices 402. For instance, the service can include voice and/ordata service. The serving network 402 communicates the registrationmessage to the home network 406 via a communication link 410. It is tobe appreciated that the communication link 410 can be the same as orshare properties with the communication link 408. The home network 406authenticates the registration attempt, and instructs the servingnetwork 404 to accept or deny the registration attempt. Based on theinstruction received from the home network 406, the serving network 404can register the mobile device 402 or reject the mobile device 402. Ifthe mobile device's 402 registration attempt is rejected, the servingnetwork 404 will transmit a rejection notification (e.g. locationupdating reject message, GPRS attach reject message, etc.) to the mobiledevice 402.

A registration request made by the mobile device 402 can be rejected fora plurality of reasons. For example, a mobile device 402 can be rejectedfor attempting to register with a serving network 404 in a locationwhere the mobile device is not authorized to roam or where roaming isrestricted. In addition, the mobile device 402 can be rejected if themobile device has not been activated with the system operator (e.g.service provider). The rejection notification can include data regardingthe status or reason of the rejection, such as a rejection cause code.

Referring to FIG. 5, an example wireless communication system 500 isshown in accordance with an embodiment of the subject application. Thesystem 500 includes a mobile device 502 and a wireless communicationnetwork 504. The mobile device 502 and wireless communication network504 can be communicately coupled via a plurality of techniques that arewell known in the art.

The mobile device 502 includes a registration component 506 and aUniversal Integrated Circuit Card (UICC) Component 508. In operation,when the mobile device 502 desires to communicate with or through thewireless communication network 504, the registration component 506transmits one or more registration request messages to the wirelesscommunication network 504. As previously discussed, the wirelesscommunication network 504 can determine to accept or reject theregistration request based at least in part on the registration requestmessage. For instance, the registration request message may include asubscriber identifier. Based on the subscriber identifier the wirelesscommunication network 504 can determine whether the mobile device hassufficient access privileges to be granted registration.

In the event that the registration request is rejected, the network 504sends a rejection notification (e.g. location updating reject message,GPRS attach reject message, etc.) to the mobile device 502. Therejection notification can include data regarding the rejection such asthe type of rejection, and/or the origin of the rejection. For instance,the rejection notification can indicate whether the rejection was for a2 g or 3 g network, or whether the rejection was for a circuit switched(CS) or packet switched (PS) registration request, and so forth. Theregistration component 506 can send the rejection notification, or adata packet containing information based on the rejection notification,to the UICC component 508.

The UICC component 508 (e.g. smart card) can process and/or store data.For instance, the UICC component 508 can obtain the rejectioninformation, and based on the type of rejection instruct the device totake some action. Additionally, the UICC component 508 can log, track,or otherwise store the data relating to the rejection.

FIG. 6 illustrates an example UICC component 602 in accordance with anaspect of the subject application. The UICC component 602 includes alogic component 604, a data store 606, and an interface component 608.The logic component 604 can be an integrated circuit that is cable ofprocessing data, wherein the UICC component 604 contains one or moreapplications and the logic component 604 can process the data via theapplications and produce an output. The data store 606 can be anon-volatile storage memory capable of storing multiple data items, suchas rejection notification data and UICC applications. The interfacecomponent 608 can include any suitable and/or necessary adapters,connectors, channels, communication paths, etc. to integrate the UICCcomponent 602 into virtually any operating and/or database system(s).For instance, the interface component 402 can enable the UICC component602 to communicate with a communication framework 608.

As previously discussed, the UICC component 602 can obtain registrationrejection notification data. The logic component 604 can analyze therejection notification data, and based on the rejection notificationdata determine an action to take based on the rejection. For instance,the logic component 604 can determine that the mobile device (not shown)should display a message to the user based on the rejection notificationdata, such as “this device has not been activated, please contactcustomer service.”

Additionally or alternatively, the UICC component 602 can log, track, orotherwise store the rejection notification data in the data store 606.For instance, the UICC component 602 can report or send the rejectionnotification to a server 612 via the interface component 608 andcommunication framework 610, wherein the server 612 is associated with aservice provider. The reported rejection notifications can be retrievedfrom the server and analyzed by the service provider.

In addition, the interface component 608 enables a customer serviceagent 614 to access the rejection notification data stored in the datastore 606. For instance, a mobile device user may contact their serviceprovider upon receiving a rejection notification. The customer serviceagent 614 can access the rejection notification data in the data store606, and based on the rejection notification data appropriately assistthe user.

FIG. 7 is an example envelope 700 for facilitating rejectionnotification to the UICC. The envelope 700 includes a plurality of datafields (e.g. 702-720) that facilitate the UICC in determining a courseof action based on the event download. For example, the envelope 700 caninclude an event download tag 702, a length field 704, an event list706, a device identities field 708, a location area identification field710, a routing area identification 712, an access technology field 714,a domain field 716, an update/attach type field 718, and/or a rejectioncause code 720.

The event download tag 702 contains data or an identifier that informsthe UICC that the envelope 700 is for an event download. The lengthfield 704 identifies the total length of the envelope 700. The length ofthe envelope 700 can be expressed in bytes, and can be the sum of thefields in the envelope 700. For instance, the length of the envelope 700can be the sum of the bytes in the event list 706, plus the bytes in thedevice identities field 708, plus the number of bytes in either thelocation area identification field 710 or routing area identificationfield 712 (discussed infra), plus the number of bytes in the accesstechnology field 714, plus the bytes contained in the domain field 716,plus the total bytes in update/attach field 718, and the bytes used forthe rejection cause code 720.

The event list field 706 can contain an event, such as a networkrejection event. The event list field 706 is set by the mobile device(e.g. UE, etc.). The device identities field 708 can contain dataregarding the source and destination of the event. For instance, thedevice identities field 708 can include a source and destinationsub-field, wherein the mobile device can set the source as being thenetwork, and the destination as being the UICC for a network rejectionevent.

Additionally, the envelope can include either a location areaidentification field 710 that contains an identification of the locationarea of the rejecting network for location updating reject message, or arouting area identification field 712 containing identificationinformation of the routing area relating to the rejecting network for ageneral packet radio system (GPRS) attach reject message.

The access technology field 714 can contain information relating to theaccess technology for the rejecting network. The domain field 716 can beused by the terminal to indicate to the UICC the domain in which therejection was received (e.g. CS or PS). The update/attach type field 718can contain information indicating to the UICC the update and/or attachtype of the location updating request, GPRS attach request, or routingarea updating request message that was sent. In the case of a locationupdate reject message, the rejection cause code field 720 can containthe cause for rejection as received in the message. Where there is aGPRS attach reject message, the rejection cause code field 720 cancontain the GMM cause information. It is to be appreciated that thesubject envelope 720 is but one example of how a registration rejectioncan be reported to the UICC, and a plurality of techniques are possiblewithin the scope and spirit of this application.

In view of the exemplary systems described supra, a methodology that maybe implemented in accordance with the disclosed subject matter will bebetter appreciated with reference to the flow chart of FIG. 8. While forpurposes of simplicity of explanation, the methodologies are shown anddescribed as a series of blocks, it is to be understood and appreciatedthat the claimed subject matter is not limited by the order of theblocks, as some blocks may occur in different orders and/or concurrentlywith other blocks from what is depicted and described herein. Moreover,the illustrated blocks do not represent all possible steps, and not allillustrated blocks may be required to implement the methodologiesdescribed hereinafter.

Referring now to FIG. 8, an example flow chart illustrating a method 800for reporting registration rejections to the UICC is shown in accordancewith an aspect of the present application. At 802, a mobile device (e.g.UE, etc.) attempts to register with a network. As discussed previously,the mobile device sends a registration message to the network requestingregistration. At 804, the device obtains a rejection notification. Arejection can occur for a plurality of reasons, such as restrictedroaming access or the device has not been activated.

At 806, the mobile device reports the rejection notification to theUICC. The mobile device can use an envelope structure (as illustrated inFIG. 7) to report the rejection notification to the UICC. The UICC candetermine an action or a course of action to take at 808. The UICC candetermine the action(s) based at least in part on the rejectionnotification data or based on predetermined set of instructions. Forinstance, the UICC can receive the rejection notification, and based onthe cause for rejection can instruct the mobile device to display amessage to a user. Additionally or alternatively, the UICC can log,track, or otherwise store the rejection notifications, wherein therejection notifications can be acquired by the service provider (aspreviously discussed) or transmitted to a server associated with theservice provider. Moreover, the UICC can implement or run one or moreapplications based on the rejection data.

FIG. 9 illustrates an approach 900 that employs an artificialintelligence (AI) component 902 which facilitates automating one or morefeatures in accordance with the subject application. The subjectapplication (e.g., in connection with inferring) can employ variousAI-based schemes for carrying out various aspects thereof. For example,a process for adding dithering could be facilitated by artificialintelligence.

A classifier is a function that maps an input attribute vector, x=(x1,x2, x3, x4, xn), to a confidence that the input belongs to a class, thatis, f(x)=confidence(class). Such classification can employ aprobabilistic and/or statistical-based analysis (e.g., factoring intothe analysis utilities and costs) to prognose or infer an action that auser desires to be automatically performed. For instance, depending onthe implementation a confidence can be assigned to the set of criteria,and an inference can be made as to the criteria that should be used astriggers for adding dithering.

A support vector machine (SVM) is an example of a classifier that can beemployed. The SVM operates by finding a hypersurface in the space ofpossible inputs, which hypersurface attempts to split the triggeringcriteria from the non-triggering events. Intuitively, this makes theclassification correct for testing data that is near, but not identicalto training data. Other directed and undirected model classificationapproaches include, e.g., naïve Bayes, Bayesian networks, decisiontrees, neural networks, fuzzy logic models, and probabilisticclassification models providing different patterns of independence canbe employed. Classification as used herein also is inclusive ofstatistical regression that is utilized to develop models of priority.

As will be readily appreciated from the subject specification, thesubject application can employ classifiers that are explicitly trained(e.g., via a generic training data) as well as implicitly trained (e.g.,via observing user behavior, receiving extrinsic information). Forexample, SVM's are configured via a learning or training phase within aclassifier constructor and feature selection module. Thus, theclassifier(s) can be used to automatically learn and perform a number offunctions, including but not limited to determining according to apredetermined criteria when to update or refine the previously inferredschema, tighten the criteria on the inferring algorithm based upon thekind of data being processed (e.g., primary versus secondary, staticversus dynamic, . . . ), and at what time of day to implement tightercriteria controls (e.g., in the evening when system performance would beless impacted).

Referring now to FIG. 10, illustrated is a schematic block diagram of aportable hand-held terminal device 1000 according to one aspect of theapplication, in which a processor 1002 is responsible for controllingthe general operation of the device 1000. The processor 1002 isprogrammed to control and operate the various components within thedevice 1000 in order to carry out the various functions describedherein. The processor 1002 can be any of a plurality of suitableprocessors. The manner in which the processor 1002 can be programmed tocarry out the functions relating to the application will be readilyapparent to those having ordinary skill in the art based on thedescription provided herein.

A memory 1004 connected to the processor 1002 serves to store programcode executed by the processor 1002, and serves as a storage means forstoring information such as user credential and receipt transactioninformation and the like. The memory 1004 can be a nonvolatile memorysuitably adapted to store at least a complete set of the informationthat is displayed. Thus, the memory 1004 can include a RAM or flashmemory for high-speed access by the processor 1002 and/or a mass storagememory, e.g., a micro drive capable of storing gigabytes of data thatcomprises text, images, audio, and video content. According to oneaspect, the memory 1004 has sufficient storage capacity to storemultiple sets of information, and the processor 1002 could include aprogram for alternating or cycling between various sets of displayinformation.

A display 1006 is coupled to the processor 1002 via a display driversystem 1008. The display 1006 can be a color liquid crystal display(LCD), plasma display, or the like. In this example, the display 1006 isa ¼ VGA display with sixteen levels of gray scale. The display 1006functions to present data, graphics, or other information content. Forexample, the display 1006 can display a set of customer information,which is displayed to the operator and can be transmitted over a systembackbone (not shown). Additionally, the display 1006 can display avariety of functions that control the execution of the device 1000. Thedisplay 1006 is capable of displaying both alphanumeric and graphicalcharacters.

Power is provided to the processor 1002 and other components forming thehand-held device 1000 by an onboard power system 1010 (e.g., a batterypack). In the event that the power system 1010 fails or becomesdisconnected from the device 1000, a supplemental power source 1012 canbe employed to provide power to the processor 1002 and to charge theonboard power system 1010. The processor 1002 of the device 1000 inducesa sleep mode to reduce the current draw upon detection of an anticipatedpower failure.

The terminal 1000 includes a communication subsystem 1014 that includesa data communication port 1016, which is employed to interface theprocessor 1002 with a remote computer. The port 1016 can include atleast one of Universal Serial Bus (USB) and IEEE 1394 serialcommunications capabilities. Other technologies can also be included,for example, infrared communication utilizing an infrared data port.

The device 1000 can also include a radio frequency (RF) transceiversection 1018 in operative communication with the processor 1002. The RFsection 1018 includes an RF receiver 1020, which receives RF signalsfrom a remote device via an antenna 1022 and demodulates the signal toobtain digital information modulated therein. The RF section 1018 alsoincludes an RF transmitter 1024 for transmitting information to a remotedevice, for example, in response to manual user input via a user inputdevice 1026 (e.g., a keypad) or automatically in response to thecompletion of a transaction or other predetermined and programmedcriteria. The transceiver section 1018 facilitates communication with atransponder system, for example, either passive or active, that is inuse with product or item RF tags. The processor 1002 signals (or pulses)the remote transponder system via the transceiver 1018, and detects thereturn signal in order to read the contents of the tag memory. In oneimplementation, the RF section 1018 further facilitates telephonecommunications using the device 1000. In furtherance thereof, an audioI/O section 1028 is provided as controlled by the processor 1002 toprocess voice input from a microphone (or similar audio input device)and audio output signals (from a speaker or similar audio outputdevice).

In another implementation, the device 1000 can provide voice recognitioncapabilities such that when the device 1000 is used simply as a voicerecorder, the processor 1002 can facilitate high-speed conversion of thevoice signals into text content for local editing and review, and/orlater download to a remote system, such as a computer word processor.Similarly, the converted voice signals can be used to control the device1000 instead of using manual entry via the keypad 1026.

Onboard peripheral devices, such as a printer 1030, signature pad 1032,and a magnetic strip reader 1034 can also be provided within the housingof the device 1000 or accommodated externally through one or more of theexternal port interfaces 1016.

The device 1000 can also include an image capture system 1036 such thatthe user can record images and/or short movies for storage by the device1000 and presentation by the display 1006. Additionally, a dataformreading system 1038 is included for scanning dataforms. It is to beappreciated that these imaging systems (1036 and 1038) can be a singlesystem capable of performing both functions.

What has been described above includes examples of the application. Itis, of course, not possible to describe every conceivable combination ofcomponents or methodologies for purposes of describing the subjectapplication, but one of ordinary skill in the art may recognize thatmany further combinations and permutations of the application arepossible. Accordingly, the application is intended to embrace all suchalterations, modifications and variations that fall within the spiritand scope of the appended claims. Furthermore, to the extent that theterm “includes” is used in either the detailed description or theclaims, such term is intended to be inclusive in a manner similar to theterm “comprising” as “comprising” is interpreted when employed as atransitional word in a claim.

What is claimed is:
 1. A method, comprising: receiving, by a networkdevice comprising a processor, registration request data related to aregistration request from a mobile device; sending, by the networkdevice, the registration request data to a home network device; inresponse to the sending the registration request data to the homenetwork device, receiving, by the network device, registration rejectiondata associated with a rejection of the registration request from thehome network device; and in response to the receiving the registrationrejection data from the home network device, sending, by the networkdevice, the registration rejection data to the mobile device.
 2. Themethod of claim 1, wherein the receiving the registration request datacomprises receiving the registration request data via a first frequencyband and the sending the registration rejection data comprises sendingthe registration rejection data via a second frequency band, and whereinthe first frequency band and the second frequency band are differentfrequency bands.
 3. The method of claim 1, wherein the receiving theregistration request data comprises receiving the registration requestdata via a first frequency band and the sending the registrationrejection data comprises sending the registration rejection data via asecond frequency band, and wherein the first frequency band and thesecond frequency band are a same frequency band.
 4. The method of claim1, wherein the registration request data comprises a type ofregistration requested.
 5. The method of claim 4, wherein the type ofregistration requested comprises a circuit switched registration.
 6. Themethod of claim 4, wherein the type of registration requested comprisesa packet switched registration.
 7. The method of claim 1, wherein theregistration rejection data comprises a registration rejection statusand a registration rejection cause code.
 8. The method of claim 7,wherein the registration rejection cause code indicates that therejection is due to a location of the mobile device.
 9. A system,comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: receiving registration requestdata related to a registration request from a universal integratedcircuit card of a mobile device, wherein the registration request datacomprises a subscriber identity of the mobile device; sending theregistration request data to a network device of a network; receivingregistration rejection data associated with a rejection of theregistration request by the network device; and sending the registrationrejection data to the universal integrated circuit card of the mobiledevice.
 10. The system of claim 9, wherein the operations furthercomprise: receiving, from the universal integrated circuit card of themobile device, display data associated with a display screen of themobile device.
 11. The system of claim 10, wherein the display datacomprises an indication that the registration rejection data wasdisplayed on the display screen of the mobile device.
 12. The system ofclaim 11, wherein the operations further comprise: transmitting thedisplay data to a service provider identity associated with the system.13. The system of claim 11, wherein the operations further comprise:transmitting an image capture of the display data to a service providerdevice of a service provider identity associated with the system. 14.The system of claim 13, wherein the operations further comprise: inresponse to the transmitting the image capture of the display data tothe service provider device, sending registration acceptance data,associated with an acceptance of the registration request, to theuniversal integrated circuit card of the mobile device.
 15. The systemof claim 9, wherein the operations further comprise: in response to anaction determined by the universal integrated circuit card, sending datato a service provider device of a service provider identity associatedwith the network device.
 16. The system of claim 15, wherein the actiondetermined by the universal integrated circuit card is in response to ananalysis of the registration rejection data.
 17. A machine-readablestorage medium, comprising executable instructions that, when executedby a processor, facilitate performance of operations, comprising: inresponse to receiving registration request data associated with a firstregistration request from an integrated circuit card of a mobile device,sending registration rejection data associated with a rejection of thefirst registration request, wherein the registration rejection datacomprises registration rejection code data associated with aregistration rejection based on a first location of the mobile device;receiving, from the integrated circuit card, analysis data related to ananalysis of the registration rejection code data; and receiving a secondregistration request, wherein the second registration request isinitiated in response the mobile device moving to a second locationbased on the analysis of the registration rejection code data.
 18. Themachine-readable storage medium of claim 17, wherein the firstregistration request comprises a circuit switched registration request.19. The machine-readable storage medium of claim 18, wherein the secondregistration request comprises a packet switched registration request.20. The machine-readable storage medium of claim 19, wherein the packetswitched registration request is facilitated in response to a conditionbeing determined to have been satisfied, and wherein the condition isassociated with the circuit switched registration request.